Adding Fields

You may find that you want certain fields to appear on a screen, form or message template that are not displayed by default. You can either add fields that already exist in the system, or create new custom fields and add them. Alternatively, you can import fields from Excel or previously saved HTML files.

Before you start

Before working in Designer, we strongly recommend that you undertake appropriate training.

Exercise caution when using the Designer to modify screen designs which have been customized by Alemba Professional Services. Contact your Alemba account manager if you are uncertain about whether your actions will impact these customizations.

You must have Designer selected in your General Access security role before you can use this option.

If the field you want to add does not already exist in vFire Core, you need to create it first.

If you want to use a field that is held in an Excel or HTML file, you need to import it first.

It is important to know where to add a field. Fields created within a task can only be used in that specific task. To pass information from one task to another, the field must be added to the parent request.

To maintain an audit trail of changes made to screens, forms and message templates, Designer must be selected in the Auditing window.

  1. Open the screen, if it is not already displayed. (Having selected the screen, select .)
  2. Make the Add a Field tab in the left hand pane uppermost, if necessary . The pane lists the fields and layout elements available to add to the current screen.
  3. In the Data fields for field, select the screen set to which the field belongs from the drop down list. This list usually includes the following values:
    • the name of the screen set(s) associated with the currently opened screen
    • For Task or Approval screens, the Request screen set linked to the screen
    • For User Survey screens, the Call screen set that is linked to the screen. The fields can only be added as read-only fields.
    • For message templates, the Sender and Recipient screen sets. You can select one of these to add fields relating to person data (such as Full Name, Email ID and Time Zone).
    • Other Screen Sets
  4. If you select a screen set associated with the current screen, you can select one of the following filter options to narrow the list of fields associated with the screen set:
  5. All fields Select this option to display all available fields
    Custom fields Select this option to see only the user-defined fields you have added
    Linked Fields

    Select this to view the fields referenced by (linked to) the current screen through an entity Q/D field. For example, a Person Q/D field displays the Person Details fields such as First Name, and Surname. Linked fields can only be added to screens as read-only fields.

    Select the field on the screen design in the main pane. The window changes. Select the Add a Field tab in the left pane once more to see that this button is now active.

  6. If you select Other Screen Sets, you can search for custom fields using the button. All Knowledge screen sets are grouped under Base Knowledge. All Task screen sets are grouped under Base Task. All Report screens are grouped under Report, Report Schedule and Generated Report.
  7. Find the field you want to add to the screen. You can sort the fields by selecting a column heading. The available fields are listed in the table in the left pane. (You may like to adjust the column widths to see all of the columns.) The following information is displayed:
  8. Display Title the display name for field shown in the application when the field is referenced
    Database Name the database name of the field (by default, is set to the display name in uppercase, with spaces converted to underscores)
    Last Modified Date the date and time when the field was created, linked to a screen set, or any field settings changed

  9. Select the field you want to add to the screen, and drag it onto the screen. Position the field where you want it to appear. An arrow with a small box, with the name of the field in a faint shaded area beneath it indicates that the field can be dropped in this area. A circle with a line through it indicates that you cannot position the field here.
  10. The Call Details, Request Details and CMDB Item Details screens may be used as templates. If you insert a field into an area of the screen only shown when the screen is in ‘template mode’, the fields will not display if the screen is being used as a standard Details window.

    When you insert a custom field into a message template, the name displayed between the [square brackets] is not the database name that displays in the list of available fields. To view the database name of the field, select the field and view the Display Name in the Field Settings tab .

  11. Select at the bottom of the window to save changes to the current screen or to save the content as an HTML file. The file can then be edited with any HTML editor. However, you should be aware that any instability as a result of modifications made outside the Designer is not covered by your Alemba support and maintenance agreement. When you export a screen, form or message template, images embedded on to the template are not exported. When you load an exported screen, form or message template into vFire Core, you will need to re-add any images. saves changes to all open screens. If auditing is turned on, the Change Reasons window will display, prompting you to add a change reason.

  12. If you insert an extensible field which was not already associated with the screen set for the current screen, the field is linked to the screen and added to the Custom fields associated with the screen set.

  13. If you wish to undo the addition, select the button in the top right corner of the window. Save the changes once more.